Bump go-flashduty 0.3.0 -> 0.4.0, which now documents the endpoints these
previously-deferred commands needed, and move them off the hand-written
flashduty-sdk onto the typed ctx.GFClient.

Migrated (legacy SDK call -> go-flashduty method):
- change list            ListChanges                     -> Changes.List
- statuspage list        ListStatusPages                 -> StatusPages.ReadPageList (page-id filter applied client-side)
- incident war-room create        CreateIncidentWarRoom            -> Incidents.WarRoomCreate
- incident war-room create (auto) ListWarRoomEnabledDataSources    -> ImIntegrations.List
- incident war-room add-member    AddIncidentWarRoomMembers        -> Incidents.WriteAddWarRoomMember
- incident war-room default-observers GetIncidentWarRoomDefaultObservers -> Incidents.ReadGetWarRoomDefaultObservers
- mcp create             CreateMCPServer                 -> McpServers.WriteServerCreate

Output (columns, order, footers, TOON) preserved exactly. change list now
clamps non-positive --limit/--page to the legacy defaults (20/1) before
sending, since go-flashduty forwards values verbatim and the server rejects
< 1; the footer still shows the raw --page value, matching legacy behavior.
statuspage list STATUS column stays empty (the /status-page/list endpoint and
the legacy SDK never populated overall_status).

Kept on legacy (no clean go-flashduty equivalent):
- statuspage changes  -> hits /status-page/change/active/list; go-flashduty only
  has the general /status-page/change/list (different semantics, requires status).
- insight notifications -> go-flashduty Analytics has no notification-trend endpoint.
Both annotated with TODO(go-flashduty migration). The shape/enrichment-deferred
commands (incident list/get/timeline/feed/similar/postmortem/update, alert
list/get/timeline, oncall who/schedule, statuspage create-incident, insight
responder, monit-query rows) remain on legacy as before.

Dropped the now-unused war-room/change/statuspage-list/mcp methods from the
flashdutyClient interface (incl. 3 war-room methods left dead by the prior
migration) and the orphaned mockClient/mockIncidentWarRoom stubs. Migrated the
affected unit tests onto the gfStub httptest seam (added a path-aware payload
hook for war-room create's two-call auto-discover flow) and added gfStub-backed
tests for change list, statuspage list, and mcp create.

flashduty-sdk dependency retained for the commands still on legacy.

The notifications command's backing report API (/report/* QueryNotificationTrend)
is being retired, so it is intentionally excluded from go-flashduty's spec — there
is no SDK method and there won't be one. Reword the TODO from a pending-migration
note to an explicit do-not-migrate so it isn't re-pointed at the SDK later.

The notification-trend report API backing this command is being taken
offline, so the command is removed outright rather than kept on the legacy
SDK. Drops the cobra subcommand, its flashdutyClient.QueryNotificationTrend
interface method, and the mockClient stub. No other caller referenced it.

Move the last two read commands that were pinned to the hand-written SDK onto
go-flashduty:

- insight responder: now calls Analytics.ByResponder. Drops the EMAIL column —
  the backend /insight/responder (RspdIncMetrics) never returns an email, so the
  legacy SDK's ResponderInsightItem.Email was always blank (a decode-only field).
- incident feed: now calls Incidents.Feed. go-flashduty returns raw feed items,
  so resolveFeedOperators() replicates the legacy operator-name enrichment by
  resolving each entry's creator_id via Members.PersonInfos (best-effort; falls
  back to the numeric ID, or 'system' for creator_id 0).

Removes the now-dead GetIncidentFeed + QueryInsightByResponder from the
flashdutyClient interface and mockClient, and rewrites the feed-empty test to use
the gfStub httptest seam. Build/vet/gofmt/test green; both commands live-verified
against api-dev (responder lists real data sans EMAIL; feed resolves operator
names).

… go-flashduty

Drops the hand-written flashduty-sdk dependency entirely. Every command now
builds a concrete *go-flashduty.Client; the shared flashdutyClient interface,
mockClient, and the legacy newClient factory are removed.

- Migrate the remaining ~25 legacy commands (alert, channel, escalation-rule,
  field, incident, insight, member, monit-query, oncall, postmortem,
  status-page, status-page-migrate, team) onto typed go-flashduty services.
- whoami/login: resolve identity via Members.MemberInfo + Account.Info.
- template: vendor the client-side authoring metadata (channels, size limits,
  variable/function catalogs) into internal/cli/templatemeta.go -- it is
  reference data, not an API surface, so the generated SDK does not carry it.
- Delete the change-trend command (backed by the retired /report/* API).
- Rewrite all legacy-mock tests onto the httptest gfStub harness.
- go.mod: drop flashduty-sdk; bump go-flashduty 0.4.0 -> 0.4.1
  (adds StatusPages.ChangeActiveList).

Verified: build, vet, test, gofmt, go mod tidy clean; whoami, member list,
incident list, template get-preset/variables live-verified against api-dev.

go-flashduty v0.5.0 turns tri-state request fields into Go pointers so the
zero value (false/0) reaches the wire instead of being dropped by omitempty.
Adopt it in the CLI consumers the compiler flagged:

- alert list: --active -> IsActive=Bool(true), --recovered -> IsActive=Bool(false),
  --muted -> EverMuted=Bool(true). --recovered (is_active=false) now actually
  filters instead of being silently dropped. Also drop the dead --title no-op
  flag (no title filter on the API; 'follow the API').
- incident similar: Limit -> Int64(limit) (flag default 5, always sent).
- statuspage migrate structure: forward --url-name as URLName=String(...) when
  provided; nil reuses the source page's name. Was previously rejected because
  the SDK lacked the field; v0.5.0 adds it.

Wire-body regression tests added for alert is_active/ever_muted, the no-filter
omit case, incident similar limit, and migrate url_name forwarding.

The dual-client migration is complete; there is one client (go-flashduty).
Import it un-aliased as `flashduty`; rename newGFClient/runGFCommand/
RunContext.GFClient to newClient/runCommand/Client. Pure rename, no behavior
change.

…duty

# Conflicts:
#	go.mod

…0.5.2

- channel list: export channelRow fields with json tags so the json/toon
  printers (reflection-based, skip unexported fields) emit full rows instead
  of empty objects.
- team list: call Teams.ReadList with the --name/--page/--limit/--orderby/
  --asc/--person-id flags instead of Teams.ReadInfos with an empty body,
  which silently dropped every flag; use server-side Total for the footer.
- go-flashduty v0.5.2: named string enums now implement fmt.Stringer, fixing
  --output-format toon for incident feed/timeline and alert timeline.